Skip to content

fix: generate publish wheels for target platforms - #4007

Merged
aignas merged 9 commits into
bazel-contrib:mainfrom
tomatotomata:codex/publish-target-platforms
Aug 29, 2026
Merged

fix: generate publish wheels for target platforms#4007
aignas merged 9 commits into
bazel-contrib:mainfrom
tomatotomata:codex/publish-target-platforms

Conversation

@tomatotomata

@tomatotomata tomatotomata commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary:

  • Configure publish deps for a static list of platforms instead of host platform.
  • Add changelog and update lockfile.

This solves two issues:

  • The lock file could be different on different platforms.
  • The publish deps behave not as expected in RBE scenarios.

Fixes #3911

Comment thread MODULE.bazel Outdated
@aignas

aignas commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

/backport

@aignas

aignas commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

This would actually fix the MODULE.bazel.lock file non-reproducibility for users who are trying to use twine targets that rules_python defines.

@github-actions github-actions Bot mentioned this pull request Aug 29, 2026
5 tasks
@aignas
aignas enabled auto-merge August 29, 2026 04:57
@aignas
aignas added this pull request to the merge queue Aug 29, 2026
Merged via the queue into bazel-contrib:main with commit 8d376b3 Aug 29, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pip.parse for rules_python_publish_deps doesn't set target_platforms, so twine only resolves for the platform that evaluated the module extension

2 participants